home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group93a.txt
/
000069_icon-group-sender _Thu Feb 18 17:06:43 1993.msg
< prev
next >
Wrap
Internet Message Format
|
1993-04-21
|
3KB
Received: by cheltenham.cs.arizona.edu; Thu, 18 Feb 1993 17:14:01 MST
Date: 18 Feb 1993 17:06:43 -0600 (CST)
From: Chris Tenaglia - 257-8765 <TENAGLIA@mis.mcw.edu>
Subject: Re: Text Computing
To: ptho@seq1.loc.gov
Cc: icon-group@cs.arizona.edu
Message-Id: <01GUVHIKY5SY8WW2JA@mis.mcw.edu>
Organization: Medical College of Wisconsin (Milwaukee, WI)
X-Vms-To: IN%"ptho@seq1.loc.gov"
X-Vms-Cc: IN%"icon-group@cs.arizona.edu"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
Status: R
Errors-To: icon-group-errors@cs.arizona.edu
See original at bottom:
These comments are true. I do tons of the stuff myself. Icon lends itself
very well to this sort of thing. However, icon is a line/string oriented
system, where editors are a file/buffer oriented systems. I've worked in
DEC TPU (text processing utility) and ICON. TPU has an editor environment
and many icon-like features. But because it's tied to an editor, it hasn't
advanced as far and fast as Icon.
Over the past several years I've noticed that ICON is getting to be more
general purpose. Recently the math has been improved, there is an object
oriented dialect (IDOL), there is X-windows and graphics and many novel
computer science ideas. Perhaps the only thing it's not well suited for is
systems programming for operating and embedded systems. Although these may
come in time.
Chris Tenaglia (System Manager) | "The past explained,
Medical College of Wisconsin | the future fortold,
8701 W. Watertown Plank Rd. | the present largely appologized for."
Milwaukee, WI 53226 | Organon to The Doctor
(414)257-8765 |
tenaglia@mis.mcw.edu
-----------------------------------------------------------------------------
> From: IN%"ptho@seq1.loc.gov" 18-FEB-1993 16:30:26.06
> To: IN%"icon-group@cs.arizona.edu"
> Subj: Text Computing
> Re: John Nall's question, What is text processing?
> What are the X, Y, and Z's of text processing? Other than saying text
> processing is non-numeric computing, which is both most accurate and
> very negative, my text processing work has 3 components:
> X. Format and edit: these deserve a category of their own because they
> take the most time even for numeric computing. Include here the use
> of editors as well as use of macros and the programming of editors.
> Y. Launder: this is more general than X. Replace, filter, encrypt, code,
> and convert data. Coding for part of speech, changing end of line markers
> from UNIX to DOS conventions, compressing data, setting data up for
> use in a database, verifying (spell checkers included) legal character
> sequences are examples.
> Z. Retrieve information: locate passages with specific strings or
> patterns of strings, find discontinuous information, find information
> when strings are incorrectly spelled (fuzzy, soundex searches), build
> special purpose databases, find material according to its linguistic
> syntax, computational linguistics (ratio of hypotactic versus paratactic
> constructions)....
> Most computing can be rephrased as text processing if we include logical
> operations, e.g., we can do mathematics by directly using lookup tables:
> if a pattern of numeric characters is found, replace with values found
> in the Add table.
> Have fun,
> Phillip Lee Thomas (ptho@seq1.loc.gov) - (202) 707-3881
> Library of Congress